Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb930267da0c0417f4e514842dd6fa2ffba407fb6ba5ef4a46753e016d116410

Tx prefix hash: 475c332c885b30993b41cbe789d6864d59eceec023c53991a18f22007186471c
Tx public key: 9ab200f4deaa2d4de375c0e875e3738b2a2e1782b9c7a558dd7582abf9cd7f61
Timestamp: 1697764646 Timestamp [UCT]: 2023-10-20 01:17:26 Age [y:d:h:m:s]: 01:096:11:56:53
Block: 873421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330167 RingCT/type: yes/0
Extra: 019ab200f4deaa2d4de375c0e875e3738b2a2e1782b9c7a558dd7582abf9cd7f6102110000000333af99f4000000000000000000

1 output(s) for total of 0.783418233000 dcy

stealth address amount amount idx
00: 8d9e45604b59430f87028eb1b049524dbd9a5dba5e749918e8351fecd25c7559 0.783418233000 1328567 of 0

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": 873431, "vin": [ { "gen": { "height": 873421 } } ], "vout": [ { "amount": 783418233, "target": { "key": "8d9e45604b59430f87028eb1b049524dbd9a5dba5e749918e8351fecd25c7559" } } ], "extra": [ 1, 154, 178, 0, 244, 222, 170, 45, 77, 227, 117, 192, 232, 117, 227, 115, 139, 42, 46, 23, 130, 185, 199, 165, 88, 221, 117, 130, 171, 249, 205, 127, 97, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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