Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6b2f3a0cbd9e8ab4acc5acf50431fd540738242750cf72ad3cf48f7e0948464

Tx prefix hash: c5a8a7919b12a4fad3db6928016cddebe6aa2922541c25eae0c76513c861e3f4
Tx public key: 658f1ad005351e78d7345c683ac9eb98fa6b19fae6551e942978cb7f120cef0f
Timestamp: 1751576277 Timestamp [UCT]: 2025-07-03 20:57:57 Age [y:d:h:m:s]: 00:140:17:10:57
Block: 1318164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98831 RingCT/type: yes/0
Extra: 01658f1ad005351e78d7345c683ac9eb98fa6b19fae6551e942978cb7f120cef0f021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48ccc81b8fa86044394e08a473958d2315065d4ae9d3e4058ba7ea8a0d05e251 0.600000000000 1805837 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": 1318174, "vin": [ { "gen": { "height": 1318164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48ccc81b8fa86044394e08a473958d2315065d4ae9d3e4058ba7ea8a0d05e251" } } ], "extra": [ 1, 101, 143, 26, 208, 5, 53, 30, 120, 215, 52, 92, 104, 58, 201, 235, 152, 250, 107, 25, 250, 230, 85, 30, 148, 41, 120, 203, 127, 18, 12, 239, 15, 2, 17, 0, 0, 0, 1, 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