Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 277ecebbb731fae139c3eed0654f18b0021d3c0b7d59054e67c576b7c8b008fc

Tx prefix hash: 849bfe9a40a296b09bc447c71dc74deb8bf52db04e463353293d04dafcd03eb7
Tx public key: 68788bef871debf3633a31ea6cadfa6641dfa81b1c4de3a0d4e64b3c892a5387
Timestamp: 1749409430 Timestamp [UCT]: 2025-06-08 19:03:50 Age [y:d:h:m:s]: 00:157:17:22:14
Block: 1300826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110401 RingCT/type: yes/0
Extra: 0168788bef871debf3633a31ea6cadfa6641dfa81b1c4de3a0d4e64b3c892a5387021100000007bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5bc72963884ba972408665e28613ef62edb8469178f2f62824f0ee2782cb8c5 0.600000000000 1788377 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": 1300836, "vin": [ { "gen": { "height": 1300826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5bc72963884ba972408665e28613ef62edb8469178f2f62824f0ee2782cb8c5" } } ], "extra": [ 1, 104, 120, 139, 239, 135, 29, 235, 243, 99, 58, 49, 234, 108, 173, 250, 102, 65, 223, 168, 27, 28, 77, 227, 160, 212, 230, 75, 60, 137, 42, 83, 135, 2, 17, 0, 0, 0, 7, 191, 81, 178, 162, 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