Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f7dbde8fa395f3619b856c93a43ae5b49971f275dcd0daf9129b33cd91afcb7

Tx prefix hash: 5344cbcabfbe139b1720aa18370599b1813ca1747ae3df4a22e0a591fe849bd0
Tx public key: b470ae3d991880821859cbab450e1ddade3eb9940fb26aab50fa90a183b6a1aa
Timestamp: 1714549917 Timestamp [UCT]: 2024-05-01 07:51:57 Age [y:d:h:m:s]: 00:332:12:56:49
Block: 1012374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237713 RingCT/type: yes/0
Extra: 01b470ae3d991880821859cbab450e1ddade3eb9940fb26aab50fa90a183b6a1aa0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4247e881da4c6f02bca422bd2b94c45ac818da3f5bc8a41b206c8a3ec3a1211c 0.600000000000 1474874 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": 1012384, "vin": [ { "gen": { "height": 1012374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4247e881da4c6f02bca422bd2b94c45ac818da3f5bc8a41b206c8a3ec3a1211c" } } ], "extra": [ 1, 180, 112, 174, 61, 153, 24, 128, 130, 24, 89, 203, 171, 69, 14, 29, 218, 222, 62, 185, 148, 15, 178, 106, 171, 80, 250, 144, 161, 131, 182, 161, 170, 2, 17, 0, 0, 0, 2, 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