Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 346d972d2b0d05a7c8dc325f07b9a05196481efd17b2fe5133774ef1fcfa91fd

Tx prefix hash: db51cf7477ff7d79a3cc1a5d8ea2f1b942b3b6a78fbcaa516c46b3aa9477528d
Tx public key: 781fc2a267e28dce18e988ed38773331654a778da3e9bea848ad6fdc07a9af93
Timestamp: 1579234728 Timestamp [UCT]: 2020-01-17 04:18:48 Age [y:d:h:m:s]: 04:347:22:33:43
Block: 47291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1138149 RingCT/type: yes/0
Extra: 01781fc2a267e28dce18e988ed38773331654a778da3e9bea848ad6fdc07a9af9302110000000a2264afe6000000000000000000

1 output(s) for total of 427.864369995000 dcy

stealth address amount amount idx
00: b98c075f5e2a6bc08d041f6aeb5708fa1b3db9664ac7dbd2621593b3761d842a 427.864369995000 87392 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": 47301, "vin": [ { "gen": { "height": 47291 } } ], "vout": [ { "amount": 427864369995, "target": { "key": "b98c075f5e2a6bc08d041f6aeb5708fa1b3db9664ac7dbd2621593b3761d842a" } } ], "extra": [ 1, 120, 31, 194, 162, 103, 226, 141, 206, 24, 233, 136, 237, 56, 119, 51, 49, 101, 74, 119, 141, 163, 233, 190, 168, 72, 173, 111, 220, 7, 169, 175, 147, 2, 17, 0, 0, 0, 10, 34, 100, 175, 230, 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