Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e30e3de035094508e99572c1e9e4f71710b00769d1015eb55bd77af80410e9a2

Tx prefix hash: 8d0eed769c3634a109b547e9f1df86002382441cdac8df9225c9046c823d3c0b
Tx public key: ade1369951dc03629a7d035a1e4d9f33dc414f269ba188cc868fb2a136d31bd5
Timestamp: 1753712887 Timestamp [UCT]: 2025-07-28 14:28:07 Age [y:d:h:m:s]: 00:116:09:53:53
Block: 1335271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82034 RingCT/type: yes/0
Extra: 01ade1369951dc03629a7d035a1e4d9f33dc414f269ba188cc868fb2a136d31bd5021100000006ef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d713d547b04676eaeec9988da7dcd5331b413111c95882fcdd2b705bedcb12d5 0.600000000000 1823072 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": 1335281, "vin": [ { "gen": { "height": 1335271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d713d547b04676eaeec9988da7dcd5331b413111c95882fcdd2b705bedcb12d5" } } ], "extra": [ 1, 173, 225, 54, 153, 81, 220, 3, 98, 154, 125, 3, 90, 30, 77, 159, 51, 220, 65, 79, 38, 155, 161, 136, 204, 134, 143, 178, 161, 54, 211, 27, 213, 2, 17, 0, 0, 0, 6, 239, 34, 20, 133, 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