Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bb25413c9a8886bc32c80a9c11fbcf55b72cbd47f8f9a37c4c8293af1f88c7a

Tx prefix hash: d6f2782c5e4dccb2429456d5297b8d15b8e43ef1cf683bb955d89c053b250f2b
Tx public key: ff2215a08ca53419a9552694308140df04dbfe73818bce979ebd27fc0b11ee83
Timestamp: 1721837117 Timestamp [UCT]: 2024-07-24 16:05:17 Age [y:d:h:m:s]: 00:122:14:31:21
Block: 1072780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87726 RingCT/type: yes/0
Extra: 01ff2215a08ca53419a9552694308140df04dbfe73818bce979ebd27fc0b11ee8302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e76bb272f999790d072a3cafb2ea825d71e99f1f4ae1cd9857cd7cf0b4b082f4 0.600000000000 1545275 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": 1072790, "vin": [ { "gen": { "height": 1072780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e76bb272f999790d072a3cafb2ea825d71e99f1f4ae1cd9857cd7cf0b4b082f4" } } ], "extra": [ 1, 255, 34, 21, 160, 140, 165, 52, 25, 169, 85, 38, 148, 48, 129, 64, 223, 4, 219, 254, 115, 129, 139, 206, 151, 158, 189, 39, 252, 11, 17, 238, 131, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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