Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e957c43a1e79db33f8b56b52ecc8cb77b54c39f5577cd81f4244b4b5ea117ecb

Tx prefix hash: 21be58f352176b765d0db1b20a84ef805cb7de0a6fd864f1e1b0e7f2df6514b2
Tx public key: cb03998233b9605e74d74e207a782769610711bfa0ba1adcb3403c4d7318770c
Timestamp: 1738208296 Timestamp [UCT]: 2025-01-30 03:38:16 Age [y:d:h:m:s]: 00:138:12:14:35
Block: 1208091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98957 RingCT/type: yes/0
Extra: 01cb03998233b9605e74d74e207a782769610711bfa0ba1adcb3403c4d7318770c02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae202c80df94ef2051e7305cdb2db1ae204b63206368fd8cd8bdc761c558acd5 0.600000000000 1694818 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": 1208101, "vin": [ { "gen": { "height": 1208091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae202c80df94ef2051e7305cdb2db1ae204b63206368fd8cd8bdc761c558acd5" } } ], "extra": [ 1, 203, 3, 153, 130, 51, 185, 96, 94, 116, 215, 78, 32, 122, 120, 39, 105, 97, 7, 17, 191, 160, 186, 26, 220, 179, 64, 60, 77, 115, 24, 119, 12, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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