Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13b1c00105f2c66dfbadef69287f00b6e108f68a0e265c72bd9f0325306a4a47

Tx prefix hash: 3bb4337b3ab76aa9577a0fad0203292207d22e95a215b89daface94408457d9c
Tx public key: 040f37de1c6dd46e0f88738f037e232b78f6261b3206650988024d6a7994035c
Timestamp: 1578072853 Timestamp [UCT]: 2020-01-03 17:34:13 Age [y:d:h:m:s]: 05:062:22:02:54
Block: 37868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194900 RingCT/type: yes/0
Extra: 01040f37de1c6dd46e0f88738f037e232b78f6261b3206650988024d6a7994035c0211000000178a2ee0d9000000000000000000

1 output(s) for total of 459.757102391000 dcy

stealth address amount amount idx
00: e7a4680a2106f8124b3b9c0ae9afac6ac024bf78539f358feb1f70078a826dfa 459.757102391000 64397 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": 37878, "vin": [ { "gen": { "height": 37868 } } ], "vout": [ { "amount": 459757102391, "target": { "key": "e7a4680a2106f8124b3b9c0ae9afac6ac024bf78539f358feb1f70078a826dfa" } } ], "extra": [ 1, 4, 15, 55, 222, 28, 109, 212, 110, 15, 136, 115, 143, 3, 126, 35, 43, 120, 246, 38, 27, 50, 6, 101, 9, 136, 2, 77, 106, 121, 148, 3, 92, 2, 17, 0, 0, 0, 23, 138, 46, 224, 217, 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