Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d639eda3018e0e8ba4e58e91e1bb51d5e8f0ed41b5a563f9ef37bbf1d346eb18

Tx prefix hash: 8184ff4f661563e7a5c64681b962044c4fda95f7bdb7bd218c19d461578bcc8b
Tx public key: 6e701138cda89aa9424c98fc5719a31ca77673cc9c7a0a05f00daaf9d3d830d2
Timestamp: 1708066910 Timestamp [UCT]: 2024-02-16 07:01:50 Age [y:d:h:m:s]: 01:009:03:13:40
Block: 958620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267533 RingCT/type: yes/0
Extra: 016e701138cda89aa9424c98fc5719a31ca77673cc9c7a0a05f00daaf9d3d830d202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74a074475cc7d16284c285db8e756239069a7c3a868e4b6878437d777bddf5ab 0.600000000000 1417979 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": 958630, "vin": [ { "gen": { "height": 958620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74a074475cc7d16284c285db8e756239069a7c3a868e4b6878437d777bddf5ab" } } ], "extra": [ 1, 110, 112, 17, 56, 205, 168, 154, 169, 66, 76, 152, 252, 87, 25, 163, 28, 167, 118, 115, 204, 156, 122, 10, 5, 240, 13, 170, 249, 211, 216, 48, 210, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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