Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2329c78fab812abf4e59eb8dacb29ec9faacc64638705ccca5fdd8a2fa3326f6

Tx prefix hash: c8e615668980fbddf1bc335abcb0d373c282ca3d0dd96068adbd73d8ec3375a5
Tx public key: 0ffe6aa913f4abb8f7ccf3aadd06d5ce1e95c0ed79dd2f1e4616a6e328e3c4d4
Timestamp: 1737540673 Timestamp [UCT]: 2025-01-22 10:11:13 Age [y:d:h:m:s]: 00:146:16:11:16
Block: 1202778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104577 RingCT/type: yes/0
Extra: 010ffe6aa913f4abb8f7ccf3aadd06d5ce1e95c0ed79dd2f1e4616a6e328e3c4d4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2e85e6a7a52722575200210d5c6ebdf341be5efff756ecbb8a3209dc93a0a9d 0.600000000000 1689445 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": 1202788, "vin": [ { "gen": { "height": 1202778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2e85e6a7a52722575200210d5c6ebdf341be5efff756ecbb8a3209dc93a0a9d" } } ], "extra": [ 1, 15, 254, 106, 169, 19, 244, 171, 184, 247, 204, 243, 170, 221, 6, 213, 206, 30, 149, 192, 237, 121, 221, 47, 30, 70, 22, 166, 227, 40, 227, 196, 212, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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