Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f871223ce590d3cf8d3ab39e977b7429799f3926ffd7b2e504ec50147a002b79

Tx prefix hash: ca6045bd5b6c021444d8511be1fbf0da657fe5679b2aeaeb3cef702fe811556e
Tx public key: d3c7d43ae6e5389cdbd377b8951e7493d801e31e1b7856cac95dc64ac3cdf649
Timestamp: 1737242251 Timestamp [UCT]: 2025-01-18 23:17:31 Age [y:d:h:m:s]: 00:056:23:15:57
Block: 1200316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40536 RingCT/type: yes/0
Extra: 01d3c7d43ae6e5389cdbd377b8951e7493d801e31e1b7856cac95dc64ac3cdf6490211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c83a3b8d9a77a4e62929e0053bcf0b86692455cf4347a168b4ee95e418515e1c 0.600000000000 1686959 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": 1200326, "vin": [ { "gen": { "height": 1200316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c83a3b8d9a77a4e62929e0053bcf0b86692455cf4347a168b4ee95e418515e1c" } } ], "extra": [ 1, 211, 199, 212, 58, 230, 229, 56, 156, 219, 211, 119, 184, 149, 30, 116, 147, 216, 1, 227, 30, 27, 120, 86, 202, 201, 93, 198, 74, 195, 205, 246, 73, 2, 17, 0, 0, 0, 2, 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