Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81bf8fd6c46b3cd062096ce26bc11850f0de7c2da4c270dd76537be34d876b6c

Tx prefix hash: c84138b7d739aadc68af5a1f84a25ddddcf6187e2b20b9c748d40bce937bb4f4
Tx public key: 8aa3acdd523a42294703b4c3132bce2d601191ae9140bac02dbb628a52667539
Timestamp: 1583539833 Timestamp [UCT]: 2020-03-07 00:10:33 Age [y:d:h:m:s]: 04:314:04:12:23
Block: 77957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118980 RingCT/type: yes/0
Extra: 018aa3acdd523a42294703b4c3132bce2d601191ae9140bac02dbb628a5266753902110000002e8a2ee0d9000000000000000000

1 output(s) for total of 338.607747272000 dcy

stealth address amount amount idx
00: 307216822468aac64ff402eba5787e5cf1370cd43150a202d8efbf722f2b5795 338.607747272000 143214 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": 77967, "vin": [ { "gen": { "height": 77957 } } ], "vout": [ { "amount": 338607747272, "target": { "key": "307216822468aac64ff402eba5787e5cf1370cd43150a202d8efbf722f2b5795" } } ], "extra": [ 1, 138, 163, 172, 221, 82, 58, 66, 41, 71, 3, 180, 195, 19, 43, 206, 45, 96, 17, 145, 174, 145, 64, 186, 192, 45, 187, 98, 138, 82, 102, 117, 57, 2, 17, 0, 0, 0, 46, 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