Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64e3692120465281ad5c4a80ab0ff06fc46b474981e874d317b14d5f2e91c395

Tx prefix hash: 9448f063ba9b502ca9eb2a5599f91064d10a8bcd4b94649e4d53b22e26ff67e9
Tx public key: 803a678a0564538db70d6972ea326caf1fcb503f7d23c55dcb0fbf1990eb06d1
Timestamp: 1629046064 Timestamp [UCT]: 2021-08-15 16:47:44 Age [y:d:h:m:s]: 04:077:21:26:33
Block: 314728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087254 RingCT/type: yes/0
Extra: 01803a678a0564538db70d6972ea326caf1fcb503f7d23c55dcb0fbf1990eb06d102110000001b01f1e57f000000000000000000

1 output(s) for total of 55.613912840000 dcy

stealth address amount amount idx
00: be10bc6fe49bb724891718b97d095e5db3a838efd4dd6518e643545faecbf96f 55.613912840000 655141 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": 314738, "vin": [ { "gen": { "height": 314728 } } ], "vout": [ { "amount": 55613912840, "target": { "key": "be10bc6fe49bb724891718b97d095e5db3a838efd4dd6518e643545faecbf96f" } } ], "extra": [ 1, 128, 58, 103, 138, 5, 100, 83, 141, 183, 13, 105, 114, 234, 50, 108, 175, 31, 203, 80, 63, 125, 35, 197, 93, 203, 15, 191, 25, 144, 235, 6, 209, 2, 17, 0, 0, 0, 27, 1, 241, 229, 127, 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