Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 601898f8535ecb4e5320f5c9857b90e1b40d7bc5206f1b59912a5c8ecca2286c

Tx prefix hash: 68623a0767bc8bbf8307b35aabd359e68fdd4767bb0d7627d4af2a50b06946bd
Tx public key: c715fdf440a6e2ea55b1c02c10a2bc3f203aee43e488ac5db29d85cca9c93aa6
Timestamp: 1577604179 Timestamp [UCT]: 2019-12-29 07:22:59 Age [y:d:h:m:s]: 05:328:23:41:41
Block: 34148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1382630 RingCT/type: yes/0
Extra: 01c715fdf440a6e2ea55b1c02c10a2bc3f203aee43e488ac5db29d85cca9c93aa602110000001ce39b962a000000000000000000

1 output(s) for total of 472.992611406000 dcy

stealth address amount amount idx
00: 8254a754bf734c2dab0e7fb23452f4cf9d002fb3deee3d90da33dc4f6a020c87 472.992611406000 57472 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": 34158, "vin": [ { "gen": { "height": 34148 } } ], "vout": [ { "amount": 472992611406, "target": { "key": "8254a754bf734c2dab0e7fb23452f4cf9d002fb3deee3d90da33dc4f6a020c87" } } ], "extra": [ 1, 199, 21, 253, 244, 64, 166, 226, 234, 85, 177, 192, 44, 16, 162, 188, 63, 32, 58, 238, 67, 228, 136, 172, 93, 178, 157, 133, 204, 169, 201, 58, 166, 2, 17, 0, 0, 0, 28, 227, 155, 150, 42, 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