Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 320e2670ef4a5161d59e5dc6d908c14beae88b667ae0ff91330b03ff7a8b85b7

Tx prefix hash: 4dc64f9877d629bf791b95bcc8302883daf99d62e9bb05b828924b48632ec5b1
Tx public key: 0ff2b2d387cc3c8ab40e64108c5013d57323778e3aef639815d0cf9d6a537c31
Timestamp: 1746977704 Timestamp [UCT]: 2025-05-11 15:35:04 Age [y:d:h:m:s]: 00:194:08:53:03
Block: 1280684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136623 RingCT/type: yes/0
Extra: 010ff2b2d387cc3c8ab40e64108c5013d57323778e3aef639815d0cf9d6a537c310211000000161f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e01b28b79064fd0accbda29e77ce2d8e6d32d8a0f512a78f900941494984b8f5 0.600000000000 1768073 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": 1280694, "vin": [ { "gen": { "height": 1280684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e01b28b79064fd0accbda29e77ce2d8e6d32d8a0f512a78f900941494984b8f5" } } ], "extra": [ 1, 15, 242, 178, 211, 135, 204, 60, 138, 180, 14, 100, 16, 140, 80, 19, 213, 115, 35, 119, 142, 58, 239, 99, 152, 21, 208, 207, 157, 106, 83, 124, 49, 2, 17, 0, 0, 0, 22, 31, 144, 81, 122, 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