Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48c41c7d4f5b5734c9abfe666426abf27634de6d30f44e9e8b54cc92aa94c4bf

Tx prefix hash: 88f72c54429970e13ca1c52f8da9d00d050090fa14be1ca2823b1576dfbbfa15
Tx public key: 7af6f99a48dcc670f4ab27dc0b38f117c95bbb0bf9a82478a9af4c0f86ae8cad
Timestamp: 1726340355 Timestamp [UCT]: 2024-09-14 18:59:15 Age [y:d:h:m:s]: 00:117:18:36:20
Block: 1110121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84221 RingCT/type: yes/0
Extra: 017af6f99a48dcc670f4ab27dc0b38f117c95bbb0bf9a82478a9af4c0f86ae8cad02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52044ee37b089e7d17fa6e90aada0e09289f3992fcb8c201f594958963a2bda8 0.600000000000 1588614 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": 1110131, "vin": [ { "gen": { "height": 1110121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52044ee37b089e7d17fa6e90aada0e09289f3992fcb8c201f594958963a2bda8" } } ], "extra": [ 1, 122, 246, 249, 154, 72, 220, 198, 112, 244, 171, 39, 220, 11, 56, 241, 23, 201, 91, 187, 11, 249, 168, 36, 120, 169, 175, 76, 15, 134, 174, 140, 173, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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