Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4667be150b1173618d85606edfe6c58e3a7fcbaae4c9836c1c305a68615672e3

Tx prefix hash: cca3475af07f3aec2ec6b97cc8d0824b5ed1d46cc209996586542bb6cd96b900
Tx public key: 7544ea01eef88aa5c1c2d870142ab2e65510d2f4e061ba66a7a5c563a2a3db78
Timestamp: 1735983021 Timestamp [UCT]: 2025-01-04 09:30:21 Age [y:d:h:m:s]: 00:309:10:10:32
Block: 1189935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218648 RingCT/type: yes/0
Extra: 017544ea01eef88aa5c1c2d870142ab2e65510d2f4e061ba66a7a5c563a2a3db7802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df566fe05b10f6a48fb73187deac74d1bb03ce35d362edcfbd0d02626953e7f4 0.600000000000 1676450 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": 1189945, "vin": [ { "gen": { "height": 1189935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df566fe05b10f6a48fb73187deac74d1bb03ce35d362edcfbd0d02626953e7f4" } } ], "extra": [ 1, 117, 68, 234, 1, 238, 248, 138, 165, 193, 194, 216, 112, 20, 42, 178, 230, 85, 16, 210, 244, 224, 97, 186, 102, 167, 165, 197, 99, 162, 163, 219, 120, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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