Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d6c8d3eebed8c20816f750970baad0a34348002059ee0d1e46d066e7dd28eb7

Tx prefix hash: b2517ffdcfb9854056df0b145f9565a94703af7bd50939a88c740876b4dcec7b
Tx public key: b7e4fb11e9e7db656ede99becb9e45424380af81a0fa7b3498aa52ea6ffbfa17
Timestamp: 1716366903 Timestamp [UCT]: 2024-05-22 08:35:03 Age [y:d:h:m:s]: 01:022:19:39:44
Block: 1027436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277149 RingCT/type: yes/0
Extra: 01b7e4fb11e9e7db656ede99becb9e45424380af81a0fa7b3498aa52ea6ffbfa1702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a933e383ca7de29dd6f33479e3433a90571a5df6cd53be44cf2d0ba95dcb13d 0.600000000000 1495055 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": 1027446, "vin": [ { "gen": { "height": 1027436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a933e383ca7de29dd6f33479e3433a90571a5df6cd53be44cf2d0ba95dcb13d" } } ], "extra": [ 1, 183, 228, 251, 17, 233, 231, 219, 101, 110, 222, 153, 190, 203, 158, 69, 66, 67, 128, 175, 129, 160, 250, 123, 52, 152, 170, 82, 234, 111, 251, 250, 23, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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