Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f42d7095e80df0a5287a4a95fe80d9596d068d7300df79da08780a529d9807cb

Tx prefix hash: 6c3a182028a46cd6adc39706bd13f7da0c8f14efdd91717a66ad856319ef768c
Tx public key: 5ee501aa212c301f415dca114e03b3fe1d2e4b385344fd990082ddd91a0cd8eb
Timestamp: 1702027568 Timestamp [UCT]: 2023-12-08 09:26:08 Age [y:d:h:m:s]: 01:046:19:35:09
Block: 908550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294793 RingCT/type: yes/0
Extra: 015ee501aa212c301f415dca114e03b3fe1d2e4b385344fd990082ddd91a0cd8eb02110000000533af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df9f56fe02636142748c2ecc3652316fd1e6032c3114f0a282b5f1256302ffcc 0.600000000000 1365587 of 15

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": 908560, "vin": [ { "gen": { "height": 908550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df9f56fe02636142748c2ecc3652316fd1e6032c3114f0a282b5f1256302ffcc" } } ], "extra": [ 1, 94, 229, 1, 170, 33, 44, 48, 31, 65, 93, 202, 17, 78, 3, 179, 254, 29, 46, 75, 56, 83, 68, 253, 153, 0, 130, 221, 217, 26, 12, 216, 235, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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