Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 330eb62ea6a4077d2da6d138fd79e8d3bc50a7ffc504684843350a6902eba733

Tx prefix hash: 6d52b40403fb03642d80516657621c3ab0a73d42c27869e9870f89ee01e14796
Tx public key: fc6fe577657d0c49ad1c1de0f0ac5c3681e4f28e7e45ba4ad5056df9da565a92
Timestamp: 1736200410 Timestamp [UCT]: 2025-01-06 21:53:30 Age [y:d:h:m:s]: 00:303:14:52:05
Block: 1191722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214484 RingCT/type: yes/0
Extra: 01fc6fe577657d0c49ad1c1de0f0ac5c3681e4f28e7e45ba4ad5056df9da565a920211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0c0881719ef45d2fa919698557f35b69e976c5670f915244143c10d7378fd00 0.600000000000 1678263 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": 1191732, "vin": [ { "gen": { "height": 1191722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0c0881719ef45d2fa919698557f35b69e976c5670f915244143c10d7378fd00" } } ], "extra": [ 1, 252, 111, 229, 119, 101, 125, 12, 73, 173, 28, 29, 224, 240, 172, 92, 54, 129, 228, 242, 142, 126, 69, 186, 74, 213, 5, 109, 249, 218, 86, 90, 146, 2, 17, 0, 0, 0, 5, 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