Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 487a956fc4dfa5447a2842bb90f22b03bc3030b068f246fc7a48ad0174d57638

Tx prefix hash: 90c898957561690e818eb7107b88f6919119ca8f5d09b75bb37ab08410aa00b7
Tx public key: 4138d6e99fdbc5ff2a35dbb636dbb4d5ccb4891b7ba6dcdbdfb961afacd048b0
Timestamp: 1700145600 Timestamp [UCT]: 2023-11-16 14:40:00 Age [y:d:h:m:s]: 01:358:14:34:50
Block: 892954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515189 RingCT/type: yes/0
Extra: 014138d6e99fdbc5ff2a35dbb636dbb4d5ccb4891b7ba6dcdbdfb961afacd048b002110000000275e3f0e9000000000000000000

1 output(s) for total of 0.674951721000 dcy

stealth address amount amount idx
00: c261a77430e274778a740861f97768954dd413e5203bb66d8fac2d03c48ff523 0.674951721000 1349113 of 0

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": 892964, "vin": [ { "gen": { "height": 892954 } } ], "vout": [ { "amount": 674951721, "target": { "key": "c261a77430e274778a740861f97768954dd413e5203bb66d8fac2d03c48ff523" } } ], "extra": [ 1, 65, 56, 214, 233, 159, 219, 197, 255, 42, 53, 219, 182, 54, 219, 180, 213, 204, 180, 137, 27, 123, 166, 220, 219, 223, 185, 97, 175, 172, 208, 72, 176, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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