Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd097e9fdb94d60593d1052995411a1ae2e928f82fa21bcebe94c3ee8530cc68

Tx prefix hash: 4c8ee0d9d6e8bbabace7cb21f2881aa1cb434ace35c29298210065d568e5c6cf
Tx public key: f5c9167b12da338064cc7f3a815c105a8dd07b024f395a187bb6e03354937833
Timestamp: 1751333341 Timestamp [UCT]: 2025-07-01 01:29:01 Age [y:d:h:m:s]: 00:182:02:14:36
Block: 1316223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128392 RingCT/type: yes/0
Extra: 01f5c9167b12da338064cc7f3a815c105a8dd07b024f395a187bb6e03354937833021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd6cb27bc7a9a77dcbcf09d9e0a54db54d4c383c3bbd403b400700256a307d9b 0.600000000000 1803882 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": 1316233, "vin": [ { "gen": { "height": 1316223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd6cb27bc7a9a77dcbcf09d9e0a54db54d4c383c3bbd403b400700256a307d9b" } } ], "extra": [ 1, 245, 201, 22, 123, 18, 218, 51, 128, 100, 204, 127, 58, 129, 92, 16, 90, 141, 208, 123, 2, 79, 57, 90, 24, 123, 182, 224, 51, 84, 147, 120, 51, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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