Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc98b98f0d7f46ae44e05b66c5ce027231896e9d580150e4e32076f89df09255

Tx prefix hash: 2d1e1c69160a0290f395a875032497d51b17d7e01bb9edfbbee6a25b67498bba
Tx public key: d6e8ae10123022ffef1f79d9d169888dad87f6ebe0a66a085d83dd0e14a99e19
Timestamp: 1751692578 Timestamp [UCT]: 2025-07-05 05:16:18 Age [y:d:h:m:s]: 00:139:03:31:43
Block: 1319071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97757 RingCT/type: yes/0
Extra: 01d6e8ae10123022ffef1f79d9d169888dad87f6ebe0a66a085d83dd0e14a99e19021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b07dcb097f693e1333b69e1cf8a793f21fb8725b0d061cf884591f1965acda2e 0.600000000000 1806760 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": 1319081, "vin": [ { "gen": { "height": 1319071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b07dcb097f693e1333b69e1cf8a793f21fb8725b0d061cf884591f1965acda2e" } } ], "extra": [ 1, 214, 232, 174, 16, 18, 48, 34, 255, 239, 31, 121, 217, 209, 105, 136, 141, 173, 135, 246, 235, 224, 166, 106, 8, 93, 131, 221, 14, 20, 169, 158, 25, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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