Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 241a1a5431c47915616ad854fe39385cd921f3b0f0a8ac5c6cb6341efaefea10

Tx prefix hash: 38e8b24e87419257c7a9810a66f12ce56f82f86079baa1a1ae788f52aa7082ec
Tx public key: d5d1e6d8d5dcdf90e06ab1964af7ddba99d554efe2d148339098b88d3c9c4502
Timestamp: 1737772800 Timestamp [UCT]: 2025-01-25 02:40:00 Age [y:d:h:m:s]: 00:147:15:27:36
Block: 1204701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105222 RingCT/type: yes/0
Extra: 01d5d1e6d8d5dcdf90e06ab1964af7ddba99d554efe2d148339098b88d3c9c45020211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a13e33cc1c0c4eb41a99164341df0c472957405af9e706573f4267fe0677f518 0.600000000000 1691392 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": 1204711, "vin": [ { "gen": { "height": 1204701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a13e33cc1c0c4eb41a99164341df0c472957405af9e706573f4267fe0677f518" } } ], "extra": [ 1, 213, 209, 230, 216, 213, 220, 223, 144, 224, 106, 177, 150, 74, 247, 221, 186, 153, 213, 84, 239, 226, 209, 72, 51, 144, 152, 184, 141, 60, 156, 69, 2, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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