Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42c22faa133838202b3ff1f2b5b7f91dab66b4a85c1a5d2c07198049d4600430

Tx prefix hash: c0885c5d389b87cac0385a28a958b01e6c9b70dd6676193280974f5d8cb7cb9f
Tx public key: 224fdb4001a3535b54ec4fc59fbf401d79d0ce15386a05b5a3bd4451dab429b3
Timestamp: 1700639633 Timestamp [UCT]: 2023-11-22 07:53:53 Age [y:d:h:m:s]: 01:071:02:40:49
Block: 897042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311972 RingCT/type: yes/0
Extra: 01224fdb4001a3535b54ec4fc59fbf401d79d0ce15386a05b5a3bd4451dab429b302110000000775e3f0e9000000000000000000

1 output(s) for total of 0.654225491000 dcy

stealth address amount amount idx
00: 9375e956982dbb0190d4d270fb5917f0e5d3bfffcbd0cad51727a60ed8a5fc73 0.654225491000 1353395 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": 897052, "vin": [ { "gen": { "height": 897042 } } ], "vout": [ { "amount": 654225491, "target": { "key": "9375e956982dbb0190d4d270fb5917f0e5d3bfffcbd0cad51727a60ed8a5fc73" } } ], "extra": [ 1, 34, 79, 219, 64, 1, 163, 83, 91, 84, 236, 79, 197, 159, 191, 64, 29, 121, 208, 206, 21, 56, 106, 5, 181, 163, 189, 68, 81, 218, 180, 41, 179, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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