Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b1d4e8fbc22678420ff75f931d2e836862b0056266a8fc8679060ca0a947ea7

Tx prefix hash: 00304314be2ee0801439e9245a19555d904784c2b246eb127f5e88f6b452a5a6
Tx public key: 20d36bc8d21cdee41df9eab7a4313fa26a1ad4e944d8f611e76c04ce2a63dcc0
Timestamp: 1763427273 Timestamp [UCT]: 2025-11-18 00:54:33 Age [y:d:h:m:s]: 00:071:16:00:02
Block: 1414467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51129 RingCT/type: yes/0
Extra: 0120d36bc8d21cdee41df9eab7a4313fa26a1ad4e944d8f611e76c04ce2a63dcc00211000000038ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 863b8d13859175874aed69244ff0891017993870a1700c069ec02cdabdfe7a19 0.600000000000 1902956 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": 1414477, "vin": [ { "gen": { "height": 1414467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "863b8d13859175874aed69244ff0891017993870a1700c069ec02cdabdfe7a19" } } ], "extra": [ 1, 32, 211, 107, 200, 210, 28, 222, 228, 29, 249, 234, 183, 164, 49, 63, 162, 106, 26, 212, 233, 68, 216, 246, 17, 231, 108, 4, 206, 42, 99, 220, 192, 2, 17, 0, 0, 0, 3, 140, 235, 127, 9, 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