Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3621e50939ff3c80173384ae5b787fe18f65a2b7e5f4e9451f6c36d4e0e68a3d

Tx prefix hash: 5b6daaa86dcfeef0e2cf77071a347a62eed3cf4776b50781a30744e844998263
Tx public key: 5d7e17bb1163b086c30ccec31ba1fc1294e5a29c39d33e41b0364f0461ead2e0
Timestamp: 1731502702 Timestamp [UCT]: 2024-11-13 12:58:22 Age [y:d:h:m:s]: 00:138:08:49:48
Block: 1152830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98712 RingCT/type: yes/0
Extra: 015d7e17bb1163b086c30ccec31ba1fc1294e5a29c39d33e41b0364f0461ead2e00211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cece60b6165e9184dfe3ab57e22d79a79085c8759eda156dfb126fd21422780 0.600000000000 1638435 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": 1152840, "vin": [ { "gen": { "height": 1152830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cece60b6165e9184dfe3ab57e22d79a79085c8759eda156dfb126fd21422780" } } ], "extra": [ 1, 93, 126, 23, 187, 17, 99, 176, 134, 195, 12, 206, 195, 27, 161, 252, 18, 148, 229, 162, 156, 57, 211, 62, 65, 176, 54, 79, 4, 97, 234, 210, 224, 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