Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: df80777f617a176fa475852404e2c8850c17f8b70f1775aa78eb6bb426e9fe6b

Tx prefix hash: 6cbc21f2434208e3d90c6560c7a8661d59e360fd45784db7e7b5bdb2fa06378d
Tx public key: 4d03b1c82c1dbce4782e43ca9963652989293fcf8a1f9d918ee6f34633f420b3
Timestamp: 1731307907 Timestamp [UCT]: 2024-11-11 06:51:47 Age [y:d:h:m:s]: 00:125:12:02:14
Block: 1151218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89521 RingCT/type: yes/0
Extra: 014d03b1c82c1dbce4782e43ca9963652989293fcf8a1f9d918ee6f34633f420b3021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31df20eed175c750cd0ecd2a663726bcaac1f4e14dcda171bf0b53c6a4e3f11a 0.600000000000 1636711 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1151228, "vin": [ { "gen": { "height": 1151218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31df20eed175c750cd0ecd2a663726bcaac1f4e14dcda171bf0b53c6a4e3f11a" } } ], "extra": [ 1, 77, 3, 177, 200, 44, 29, 188, 228, 120, 46, 67, 202, 153, 99, 101, 41, 137, 41, 63, 207, 138, 31, 157, 145, 142, 230, 243, 70, 51, 244, 32, 179, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8