Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d66023d23f3b6e541f2e665b33f33c6cd7cc8a1141233f1d20a2aee33a1b734

Tx prefix hash: a69405611db0b03fd974e182d649dd6deb66e0ae2b56d1268f2e1a242f2f5c38
Tx public key: cc317f4045b8a1f959544379d4b401a2a95579d72dc530a3a667515c4756aebd
Timestamp: 1637500703 Timestamp [UCT]: 2021-11-21 13:18:23 Age [y:d:h:m:s]: 03:118:20:56:49
Block: 378994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 863644 RingCT/type: yes/0
Extra: 01cc317f4045b8a1f959544379d4b401a2a95579d72dc530a3a667515c4756aebd02110000000e4a0f5013000000000000000000

1 output(s) for total of 34.059316813000 dcy

stealth address amount amount idx
00: 680101d12db7545ad2fa1769ce4dddd314ffaf2f8ac94890707c4417af196472 34.059316813000 766236 of 0

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": 379004, "vin": [ { "gen": { "height": 378994 } } ], "vout": [ { "amount": 34059316813, "target": { "key": "680101d12db7545ad2fa1769ce4dddd314ffaf2f8ac94890707c4417af196472" } } ], "extra": [ 1, 204, 49, 127, 64, 69, 184, 161, 249, 89, 84, 67, 121, 212, 180, 1, 162, 169, 85, 121, 215, 45, 197, 48, 163, 166, 103, 81, 92, 71, 86, 174, 189, 2, 17, 0, 0, 0, 14, 74, 15, 80, 19, 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