Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8345495130c7b29e7360ae23fdf85bca44a586b962e0dd374dd311d3dbbbb8f

Tx prefix hash: 266504c2dc0f2183a0e6e4f12581313503518e3c348dfd56c9b2e1c306e3274c
Tx public key: f5bd8daca95674c04806e35cf8d459ff4bc51e2b1325c99f677afcdb89e86968
Timestamp: 1745862101 Timestamp [UCT]: 2025-04-28 17:41:41 Age [y:d:h:m:s]: 00:014:05:20:33
Block: 1271452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10164 RingCT/type: yes/0
Extra: 01f5bd8daca95674c04806e35cf8d459ff4bc51e2b1325c99f677afcdb89e8696802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc9079effaa5df66149f8aacbbb6aa4537e4ce26e4307cf5dffcab1080350945 0.600000000000 1758713 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": 1271462, "vin": [ { "gen": { "height": 1271452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc9079effaa5df66149f8aacbbb6aa4537e4ce26e4307cf5dffcab1080350945" } } ], "extra": [ 1, 245, 189, 141, 172, 169, 86, 116, 192, 72, 6, 227, 92, 248, 212, 89, 255, 75, 197, 30, 43, 19, 37, 201, 159, 103, 122, 252, 219, 137, 232, 105, 104, 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