Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b5622c4f02260c87b5afa7dcf47a57b1efd7e105919cae9212d22927470aef2

Tx prefix hash: 4b41f8b8c15f94635815fe9c5c1114a42057dc42650c9aac94df0b0a3932dd8b
Tx public key: 8d746264381be1cf49b08d28616933406e694dd425bd2c65daff1a8fca811df5
Timestamp: 1713076258 Timestamp [UCT]: 2024-04-14 06:30:58 Age [y:d:h:m:s]: 01:022:06:59:10
Block: 1000142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276907 RingCT/type: yes/0
Extra: 018d746264381be1cf49b08d28616933406e694dd425bd2c65daff1a8fca811df502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31e810a3b36facdeb22af07fdca5127d84e0b5541230ef2d0b09b11955ad605e 0.600000000000 1460634 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": 1000152, "vin": [ { "gen": { "height": 1000142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31e810a3b36facdeb22af07fdca5127d84e0b5541230ef2d0b09b11955ad605e" } } ], "extra": [ 1, 141, 116, 98, 100, 56, 27, 225, 207, 73, 176, 141, 40, 97, 105, 51, 64, 110, 105, 77, 212, 37, 189, 44, 101, 218, 255, 26, 143, 202, 129, 29, 245, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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