Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c1181c598a9c44ed1d079cb6f558c100f4746d78b7296b0bda6fc51e3746d39

Tx prefix hash: 7823a36006a8b1d7d3f4d9cd9f95ffd777320cc9bed46859f792595225e19fef
Tx public key: ba0f52505c8c246e104513f5d586555f252b6326080c060a915b4a1d2bcf00a5
Timestamp: 1721559189 Timestamp [UCT]: 2024-07-21 10:53:09 Age [y:d:h:m:s]: 00:259:11:02:47
Block: 1070474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185349 RingCT/type: yes/0
Extra: 01ba0f52505c8c246e104513f5d586555f252b6326080c060a915b4a1d2bcf00a5021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 377ae04f1177a900c23cd3f03558e05ae92e1109032e0a16cfdd65c94112f03b 0.600000000000 1542323 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": 1070484, "vin": [ { "gen": { "height": 1070474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "377ae04f1177a900c23cd3f03558e05ae92e1109032e0a16cfdd65c94112f03b" } } ], "extra": [ 1, 186, 15, 82, 80, 92, 140, 36, 110, 16, 69, 19, 245, 213, 134, 85, 95, 37, 43, 99, 38, 8, 12, 6, 10, 145, 91, 74, 29, 43, 207, 0, 165, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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