Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 744813303d177135746c745833ba0f72f079aac9bcac1b13cab26679cebdbd99

Tx prefix hash: a02c28ce8913ac2175708b5ede46b469343923f0ebb1efc688432fbbab17522d
Tx public key: 3c6a5b7c6686b1fd4a08abd76e9cf2d91e67c2d15b8990d7c3ab2e30414b417d
Timestamp: 1723502977 Timestamp [UCT]: 2024-08-12 22:49:37 Age [y:d:h:m:s]: 00:248:19:09:52
Block: 1086594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177711 RingCT/type: yes/0
Extra: 013c6a5b7c6686b1fd4a08abd76e9cf2d91e67c2d15b8990d7c3ab2e30414b417d021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 809e8f8c98e0c07671d5cf831ebec2e1cb3b4c66c22dd9831211c4c4cd942a84 0.600000000000 1561191 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": 1086604, "vin": [ { "gen": { "height": 1086594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "809e8f8c98e0c07671d5cf831ebec2e1cb3b4c66c22dd9831211c4c4cd942a84" } } ], "extra": [ 1, 60, 106, 91, 124, 102, 134, 177, 253, 74, 8, 171, 215, 110, 156, 242, 217, 30, 103, 194, 209, 91, 137, 144, 215, 195, 171, 46, 48, 65, 75, 65, 125, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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