Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b5896c24071ddc49de03cf3d21a3157df0ffc668c0d518bac2fb73cda7d7a76

Tx prefix hash: 7f00c184dca623a17f66f65c43459c5d2ead4111fa48e75e4b6177dbd6fc0c43
Tx public key: a7fd62bc6c97327ae93cd313642f7e5ebe305ec4a05d15673a9e6c66fb9e0f16
Timestamp: 1720776658 Timestamp [UCT]: 2024-07-12 09:30:58 Age [y:d:h:m:s]: 01:116:21:42:39
Block: 1064004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342044 RingCT/type: yes/0
Extra: 01a7fd62bc6c97327ae93cd313642f7e5ebe305ec4a05d15673a9e6c66fb9e0f1602110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 953cd996ec7abfe46f8d8b9d3f2d68d5497c7b3ec9a2d76256736ee7e815c50d 0.600000000000 1534525 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": 1064014, "vin": [ { "gen": { "height": 1064004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "953cd996ec7abfe46f8d8b9d3f2d68d5497c7b3ec9a2d76256736ee7e815c50d" } } ], "extra": [ 1, 167, 253, 98, 188, 108, 151, 50, 122, 233, 60, 211, 19, 100, 47, 126, 94, 190, 48, 94, 196, 160, 93, 21, 103, 58, 158, 108, 102, 251, 158, 15, 22, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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