Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06af4314d2f344751b5ab113693e4b0ca9ae57bab7fbb005df05465d27ae01dd

Tx prefix hash: 3b1b0cadc655b5dd65a08a1a5c03751d55c24bc6a46a734e64e1a60cf12a4548
Tx public key: 376000978d4c5587a5d68b88ec5f74f1a9fe190578d4b678eef98397efdd2964
Timestamp: 1744555146 Timestamp [UCT]: 2025-04-13 14:39:06 Age [y:d:h:m:s]: 00:217:04:49:17
Block: 1260629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152954 RingCT/type: yes/0
Extra: 01376000978d4c5587a5d68b88ec5f74f1a9fe190578d4b678eef98397efdd29640211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 430a2e7c7b3e32a4d087483f1f1a0ea8181092ce3e4378f99fb606834c10fc97 0.600000000000 1747790 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": 1260639, "vin": [ { "gen": { "height": 1260629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "430a2e7c7b3e32a4d087483f1f1a0ea8181092ce3e4378f99fb606834c10fc97" } } ], "extra": [ 1, 55, 96, 0, 151, 141, 76, 85, 135, 165, 214, 139, 136, 236, 95, 116, 241, 169, 254, 25, 5, 120, 212, 182, 120, 238, 249, 131, 151, 239, 221, 41, 100, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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