Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8747a702821cce530b3f16d1249ef6599b997bb544374bdef35794355592a69a

Tx prefix hash: f503b4f9e43692e278b0455c6aa383c187b9956940e8951a0debaa3ab345fee1
Tx public key: dc8532d5e11c1e72371b5666a0a129af3e96913a3a2ef0f0c202e9a3e43dac48
Timestamp: 1577911571 Timestamp [UCT]: 2020-01-01 20:46:11 Age [y:d:h:m:s]: 05:001:18:58:32
Block: 36609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151358 RingCT/type: yes/0
Extra: 01dc8532d5e11c1e72371b5666a0a129af3e96913a3a2ef0f0c202e9a3e43dac4802110000003f8a2ee0d9000000000000000000

1 output(s) for total of 464.194551372000 dcy

stealth address amount amount idx
00: 6dd8a0ab0112390a4145359bad044abf2f9c1b6fdce514d4ac2e7f8ca139dce5 464.194551372000 62053 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": 36619, "vin": [ { "gen": { "height": 36609 } } ], "vout": [ { "amount": 464194551372, "target": { "key": "6dd8a0ab0112390a4145359bad044abf2f9c1b6fdce514d4ac2e7f8ca139dce5" } } ], "extra": [ 1, 220, 133, 50, 213, 225, 28, 30, 114, 55, 27, 86, 102, 160, 161, 41, 175, 62, 150, 145, 58, 58, 46, 240, 240, 194, 2, 233, 163, 228, 61, 172, 72, 2, 17, 0, 0, 0, 63, 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