Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f2d2dc20badd83c221a01c41abd02ce735128ee44586db69424dcd60c0d2c58

Tx prefix hash: ba23e1be3f1eb9e14551e685df87b459271a698d90ebe18e258db233eb0fca4e
Tx public key: d1bc6d4b1c89453e2eee8af784c06dbebec5c98e42ffd815861a5b63e3aad590
Timestamp: 1724687002 Timestamp [UCT]: 2024-08-26 15:43:22 Age [y:d:h:m:s]: 00:136:21:58:01
Block: 1096411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97934 RingCT/type: yes/0
Extra: 01d1bc6d4b1c89453e2eee8af784c06dbebec5c98e42ffd815861a5b63e3aad590021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c4b1f4e77235d4b2f01fd672d41021e32a1538d54370cbbc94eb761169c76ad 0.600000000000 1571600 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": 1096421, "vin": [ { "gen": { "height": 1096411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c4b1f4e77235d4b2f01fd672d41021e32a1538d54370cbbc94eb761169c76ad" } } ], "extra": [ 1, 209, 188, 109, 75, 28, 137, 69, 62, 46, 238, 138, 247, 132, 192, 109, 190, 190, 197, 201, 142, 66, 255, 216, 21, 134, 26, 91, 99, 227, 170, 213, 144, 2, 17, 0, 0, 0, 2, 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