Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6d6a24bd90d45c69c3768f7d75e62c10908e5e4211709fda33ccbd911cca4f3

Tx prefix hash: 39d6a3788c503678dc58359848ede04106980b5782824cfc0fb089c37c31837b
Tx public key: 6b3770ea80858fed23e33b16286ba8b9391cc3aa20fb7ccdb0eec43f92c8dfb0
Timestamp: 1731621834 Timestamp [UCT]: 2024-11-14 22:03:54 Age [y:d:h:m:s]: 00:128:08:51:22
Block: 1153821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91556 RingCT/type: yes/0
Extra: 016b3770ea80858fed23e33b16286ba8b9391cc3aa20fb7ccdb0eec43f92c8dfb00211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c889d9b63729b3adfa0220b4a56bf726e77e3a2c3b39c40870e572d8d2a002d 0.600000000000 1639432 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": 1153831, "vin": [ { "gen": { "height": 1153821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c889d9b63729b3adfa0220b4a56bf726e77e3a2c3b39c40870e572d8d2a002d" } } ], "extra": [ 1, 107, 55, 112, 234, 128, 133, 143, 237, 35, 227, 59, 22, 40, 107, 168, 185, 57, 28, 195, 170, 32, 251, 124, 205, 176, 238, 196, 63, 146, 200, 223, 176, 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