Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22bb6921538543db29f3a12e835b456f28a13d2a1f1d0e5d322c6a59338f3037

Tx prefix hash: 03297f0e91cc327bb96bcd3ca58ba63577ae20f62bc952dc299eda108f38906c
Tx public key: a767b2d9905c5e6d994724c3cc21eeb8dd7f9d21cb40c52137777881a2f17e07
Timestamp: 1712579931 Timestamp [UCT]: 2024-04-08 12:38:51 Age [y:d:h:m:s]: 01:000:00:31:45
Block: 996009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260989 RingCT/type: yes/0
Extra: 01a767b2d9905c5e6d994724c3cc21eeb8dd7f9d21cb40c52137777881a2f17e070211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5fe1523e10289a92e299b42b090dd29a27addcb0dddf277077e2a1db46549dc 0.600000000000 1456425 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": 996019, "vin": [ { "gen": { "height": 996009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5fe1523e10289a92e299b42b090dd29a27addcb0dddf277077e2a1db46549dc" } } ], "extra": [ 1, 167, 103, 178, 217, 144, 92, 94, 109, 153, 71, 36, 195, 204, 33, 238, 184, 221, 127, 157, 33, 203, 64, 197, 33, 55, 119, 120, 129, 162, 241, 126, 7, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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