Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b151c6b2442e6f8ef96be5ff70a7444081b0ea4499beae54fbcd7445a2f6401

Tx prefix hash: 16ebbb1791fa6bb744153b78e4e0fb0dc642ba1acc94244fa7d4dabfa2821030
Tx public key: 7bdc748b7a0158b88541a9241bfbe125fe15e82703b09e08d5c09f30217dc383
Timestamp: 1717247294 Timestamp [UCT]: 2024-06-01 13:08:14 Age [y:d:h:m:s]: 00:286:05:56:35
Block: 1034745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204575 RingCT/type: yes/0
Extra: 017bdc748b7a0158b88541a9241bfbe125fe15e82703b09e08d5c09f30217dc38302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4015afeae848e5b8a6f2ee38c814eecae75dbee48e200d88af0f7e99d931e079 0.600000000000 1503264 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": 1034755, "vin": [ { "gen": { "height": 1034745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4015afeae848e5b8a6f2ee38c814eecae75dbee48e200d88af0f7e99d931e079" } } ], "extra": [ 1, 123, 220, 116, 139, 122, 1, 88, 184, 133, 65, 169, 36, 27, 251, 225, 37, 254, 21, 232, 39, 3, 176, 158, 8, 213, 192, 159, 48, 33, 125, 195, 131, 2, 17, 0, 0, 0, 5, 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