Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd67e77766b7f740b8330beed235beb228f994ad47f9d987f8ce507e631755ba

Tx prefix hash: 16e3cc7a552cbc61bb4f431e29fdede74184b319c282b674784e478beb76d10e
Tx public key: f3bcaf0e6d35e0d89dba8932e6b566bb318c4cb0d2dccd9fd9461d562a0c2c2a
Timestamp: 1721307761 Timestamp [UCT]: 2024-07-18 13:02:41 Age [y:d:h:m:s]: 01:116:13:23:07
Block: 1068409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341803 RingCT/type: yes/0
Extra: 01f3bcaf0e6d35e0d89dba8932e6b566bb318c4cb0d2dccd9fd9461d562a0c2c2a021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46f51a5fc40675d64dd0b23bcc342cae8d43acfcbe4d7a7bc9b3c3a1290585d0 0.600000000000 1539486 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": 1068419, "vin": [ { "gen": { "height": 1068409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46f51a5fc40675d64dd0b23bcc342cae8d43acfcbe4d7a7bc9b3c3a1290585d0" } } ], "extra": [ 1, 243, 188, 175, 14, 109, 53, 224, 216, 157, 186, 137, 50, 230, 181, 102, 187, 49, 140, 76, 176, 210, 220, 205, 159, 217, 70, 29, 86, 42, 12, 44, 42, 2, 17, 0, 0, 0, 8, 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