Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d700626d7f24c7497e94e3eecd36d10153b3d267dd94e02e1328910181cb730c

Tx prefix hash: f8d23f7a98a58104ac5d4b38a5b3f0af2c9e162f2f635d7f4cf6f699f4add055
Tx public key: 0289abf0ea7b1a55de7911a1a699d7de6878fad466f15f5974d58374d21e80e1
Timestamp: 1625489063 Timestamp [UCT]: 2021-07-05 12:44:23 Age [y:d:h:m:s]: 03:323:21:58:51
Block: 288634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1001210 RingCT/type: yes/0
Extra: 010289abf0ea7b1a55de7911a1a699d7de6878fad466f15f5974d58374d21e80e102110000008d0f4c30de000000000000000000

1 output(s) for total of 67.864668942000 dcy

stealth address amount amount idx
00: 4b686b413a24d2f69642736075d12661893cda75f615a5437838bc2acc3313ad 67.864668942000 604679 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": 288644, "vin": [ { "gen": { "height": 288634 } } ], "vout": [ { "amount": 67864668942, "target": { "key": "4b686b413a24d2f69642736075d12661893cda75f615a5437838bc2acc3313ad" } } ], "extra": [ 1, 2, 137, 171, 240, 234, 123, 26, 85, 222, 121, 17, 161, 166, 153, 215, 222, 104, 120, 250, 212, 102, 241, 95, 89, 116, 213, 131, 116, 210, 30, 128, 225, 2, 17, 0, 0, 0, 141, 15, 76, 48, 222, 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