Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 421f1a43e33229291b4be178b21d0cf04a8555a1b7ccb5a57e9717b6356822e8

Tx prefix hash: 8113451b1f195d87c10ef5cd9540283c6fe4632f64038cf88a93e1e3c4c009b1
Tx public key: c173ce61bfd60742e3306cb85486c7941d3e5d5beecd6d9b99c5b67ab8caaf65
Timestamp: 1735588028 Timestamp [UCT]: 2024-12-30 19:47:08 Age [y:d:h:m:s]: 00:157:17:31:46
Block: 1186653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112568 RingCT/type: yes/0
Extra: 01c173ce61bfd60742e3306cb85486c7941d3e5d5beecd6d9b99c5b67ab8caaf65021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 554cc3ea658c79d941060b6b2f6b58a16511fca7c7a65440c2ca565ecc727619 0.600000000000 1673136 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": 1186663, "vin": [ { "gen": { "height": 1186653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "554cc3ea658c79d941060b6b2f6b58a16511fca7c7a65440c2ca565ecc727619" } } ], "extra": [ 1, 193, 115, 206, 97, 191, 214, 7, 66, 227, 48, 108, 184, 84, 134, 199, 148, 29, 62, 93, 91, 238, 205, 109, 155, 153, 197, 182, 122, 184, 202, 175, 101, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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