Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 781041b7e1dd2869a2e417e610757aa3947dd404caaeb7f18fc0c62a945079f8

Tx prefix hash: cf0bdbe70a7cf67f2555f91bed83fd68b1e0c529a3771fea88f0026db9f5a15b
Tx public key: 60095f7976056f1b08f7c5be6a220aae71eeea4036709eb7532bc56a20a8af32
Timestamp: 1582449350 Timestamp [UCT]: 2020-02-23 09:15:50 Age [y:d:h:m:s]: 04:352:00:47:11
Block: 70905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1143810 RingCT/type: yes/0
Extra: 0160095f7976056f1b08f7c5be6a220aae71eeea4036709eb7532bc56a20a8af320211000000034943cd9f000000000000000000

1 output(s) for total of 357.349133913000 dcy

stealth address amount amount idx
00: c75c78261168005945be6b6ad8ab438b8590da6a213cf0ce0c2be18b4dd85480 357.349133913000 130979 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": 70915, "vin": [ { "gen": { "height": 70905 } } ], "vout": [ { "amount": 357349133913, "target": { "key": "c75c78261168005945be6b6ad8ab438b8590da6a213cf0ce0c2be18b4dd85480" } } ], "extra": [ 1, 96, 9, 95, 121, 118, 5, 111, 27, 8, 247, 197, 190, 106, 34, 10, 174, 113, 238, 234, 64, 54, 112, 158, 183, 83, 43, 197, 106, 32, 168, 175, 50, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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