Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7357fb32e1cc8942ba90a89666997ce094d467e8ce151c07b4046acc555a3795

Tx prefix hash: e4a105f7443ca82f4aa58abe0f4620fddbcb7714a0752d2c3e2e0b222a3ac338
Tx public key: 086cf8eb37d8b5b3ff3c701d519771c9c7af14fc6332e862f06544408df126f1
Timestamp: 1630651047 Timestamp [UCT]: 2021-09-03 06:37:27 Age [y:d:h:m:s]: 03:123:17:37:44
Block: 326439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 863222 RingCT/type: yes/0
Extra: 01086cf8eb37d8b5b3ff3c701d519771c9c7af14fc6332e862f06544408df126f1021100000020deae9d30000000000000000000

1 output(s) for total of 50.859552368000 dcy

stealth address amount amount idx
00: 1ad3f96c88d33a5207fe3a2612910971ea2d089849ba4addc7867c4a54dba14b 50.859552368000 676368 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": 326449, "vin": [ { "gen": { "height": 326439 } } ], "vout": [ { "amount": 50859552368, "target": { "key": "1ad3f96c88d33a5207fe3a2612910971ea2d089849ba4addc7867c4a54dba14b" } } ], "extra": [ 1, 8, 108, 248, 235, 55, 216, 181, 179, 255, 60, 112, 29, 81, 151, 113, 201, 199, 175, 20, 252, 99, 50, 232, 98, 240, 101, 68, 64, 141, 241, 38, 241, 2, 17, 0, 0, 0, 32, 222, 174, 157, 48, 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