Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc016805309b5ad5d7e31a1979b847e82a6329350a546d883f6779b10d970e87

Tx prefix hash: e6783731f6ffc5ddba528340c51927fb5951f1e3e8d05ad039ed0e2a1eda7e77
Tx public key: d625fc9c11dc431a973b2351dd24b296a12d4f1a616ab8df8049d5ac7a13ebc1
Timestamp: 1582109210 Timestamp [UCT]: 2020-02-19 10:46:50 Age [y:d:h:m:s]: 04:283:03:30:52
Block: 68084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1094806 RingCT/type: yes/0
Extra: 01d625fc9c11dc431a973b2351dd24b296a12d4f1a616ab8df8049d5ac7a13ebc10211000000174943cd9f000000000000000000

1 output(s) for total of 365.098670497000 dcy

stealth address amount amount idx
00: fef513685138025ca30e80a1c7a7211b1cbddbfa5e28b7baf2fae5aba9a1b932 365.098670497000 125450 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": 68094, "vin": [ { "gen": { "height": 68084 } } ], "vout": [ { "amount": 365098670497, "target": { "key": "fef513685138025ca30e80a1c7a7211b1cbddbfa5e28b7baf2fae5aba9a1b932" } } ], "extra": [ 1, 214, 37, 252, 156, 17, 220, 67, 26, 151, 59, 35, 81, 221, 36, 178, 150, 161, 45, 79, 26, 97, 106, 184, 223, 128, 73, 213, 172, 122, 19, 235, 193, 2, 17, 0, 0, 0, 23, 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