Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 825290421e734bd9fc58b0798500d026983d6bf8004d478fd0ec762b3b4d8a96

Tx prefix hash: e7f9460bd820da1d7d43cfae27031ec0c79b8cd25c8af14f02fd71124aa2dbaa
Tx public key: 28e3290dfa65af7e00928ea83b647948d2e8783e432d518a91f7b0b3d6308dbf
Timestamp: 1708592264 Timestamp [UCT]: 2024-02-22 08:57:44 Age [y:d:h:m:s]: 00:349:11:15:00
Block: 962979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249881 RingCT/type: yes/0
Extra: 0128e3290dfa65af7e00928ea83b647948d2e8783e432d518a91f7b0b3d6308dbf0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d7d485b868113dd43d5ff863f38799114c59cfa9b50e9fc083bc72211ff4d0e 0.600000000000 1422672 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": 962989, "vin": [ { "gen": { "height": 962979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d7d485b868113dd43d5ff863f38799114c59cfa9b50e9fc083bc72211ff4d0e" } } ], "extra": [ 1, 40, 227, 41, 13, 250, 101, 175, 126, 0, 146, 142, 168, 59, 100, 121, 72, 210, 232, 120, 62, 67, 45, 81, 138, 145, 247, 176, 179, 214, 48, 141, 191, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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