Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4120e069fe888cb0abc136f6c82954f2a00104398b3f21b06377f7953342e3e

Tx prefix hash: b29a1273524f6a71c583ebfc44603e0112e66c2ab3486b83c33d45372d4dc85a
Tx public key: d4875d2a8d206e64d39e0dfd8b146e9ffaa0aaa61fb476405c4b07561561fa5f
Timestamp: 1733985432 Timestamp [UCT]: 2024-12-12 06:37:12 Age [y:d:h:m:s]: 00:111:11:28:48
Block: 1173409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79451 RingCT/type: yes/0
Extra: 01d4875d2a8d206e64d39e0dfd8b146e9ffaa0aaa61fb476405c4b07561561fa5f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6421d99778ffb214f6c612a6cd91248c4261f656390b0bfaf2d15a46b4ee1be5 0.600000000000 1659428 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": 1173419, "vin": [ { "gen": { "height": 1173409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6421d99778ffb214f6c612a6cd91248c4261f656390b0bfaf2d15a46b4ee1be5" } } ], "extra": [ 1, 212, 135, 93, 42, 141, 32, 110, 100, 211, 158, 13, 253, 139, 20, 110, 159, 250, 160, 170, 166, 31, 180, 118, 64, 92, 75, 7, 86, 21, 97, 250, 95, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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