Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 768c61b9116e3804806a364b3ba36f82ebd712df2307045a77449d2e49860e31

Tx prefix hash: 637cc6838c35a50ad765dc4c2a553911c973a60c28d5cc3d5386155c70ca9207
Tx public key: b56837c338400dcd3495440a19da4b2d2c7e37756a559dfe6d7973fb5bf61efb
Timestamp: 1704027870 Timestamp [UCT]: 2023-12-31 13:04:30 Age [y:d:h:m:s]: 01:318:02:44:24
Block: 925132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486191 RingCT/type: yes/0
Extra: 01b56837c338400dcd3495440a19da4b2d2c7e37756a559dfe6d7973fb5bf61efb021100000006e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b3a3befe0ee82908e67b3b4fddf1847a532b5f0177d6a2ae61274674c897e4a 0.600000000000 1382892 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": 925142, "vin": [ { "gen": { "height": 925132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b3a3befe0ee82908e67b3b4fddf1847a532b5f0177d6a2ae61274674c897e4a" } } ], "extra": [ 1, 181, 104, 55, 195, 56, 64, 13, 205, 52, 149, 68, 10, 25, 218, 75, 45, 44, 126, 55, 117, 106, 85, 157, 254, 109, 121, 115, 251, 91, 246, 30, 251, 2, 17, 0, 0, 0, 6, 224, 133, 50, 182, 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