Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96986a1f40ae9f17ea210a132d22a1fd263ad94b80cb0c9f6e323b1e64d68e3b

Tx prefix hash: 14c3428641a61af51d5d505baae311c35352d34b6c256863d2911ce2111fc0e2
Tx public key: 1e15b9e98b00dd09b43dc76e88444805b0054da34ad74395f7eb687eb47315be
Timestamp: 1718844356 Timestamp [UCT]: 2024-06-20 00:45:56 Age [y:d:h:m:s]: 00:296:17:52:31
Block: 1047973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212056 RingCT/type: yes/0
Extra: 011e15b9e98b00dd09b43dc76e88444805b0054da34ad74395f7eb687eb47315be0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3401d0fc90d98102893878d9b44c619db28f69e24834eea5ad184e4ef196ca8 0.600000000000 1517936 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": 1047983, "vin": [ { "gen": { "height": 1047973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3401d0fc90d98102893878d9b44c619db28f69e24834eea5ad184e4ef196ca8" } } ], "extra": [ 1, 30, 21, 185, 233, 139, 0, 221, 9, 180, 61, 199, 110, 136, 68, 72, 5, 176, 5, 77, 163, 74, 215, 67, 149, 247, 235, 104, 126, 180, 115, 21, 190, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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