Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7453953d3c7fb933101ac77bc4f7286b020eaa19206dfa0c91ba891e76523d7c

Tx prefix hash: fadc181e3fbab3549551d69e51868a44561b770a7bd883a50ca2ad80ea85e8cb
Tx public key: 86b141d088aed3f4e31ac9257f3678cdc1e262532cd3ffafe83c2c86aa388e8b
Timestamp: 1751087994 Timestamp [UCT]: 2025-06-28 05:19:54 Age [y:d:h:m:s]: 00:134:22:52:19
Block: 1314307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94529 RingCT/type: yes/0
Extra: 0186b141d088aed3f4e31ac9257f3678cdc1e262532cd3ffafe83c2c86aa388e8b02110000000d43846d66000000000000000000

1 output(s) for total of 0.600100000000 dcy

stealth address amount amount idx
00: f99fe3ae2a085baae4f0bf8f32ee2ea11af0b27260a56c324075082c98820d4e 0.600100000000 1801952 of 0

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": 1314317, "vin": [ { "gen": { "height": 1314307 } } ], "vout": [ { "amount": 600100000, "target": { "key": "f99fe3ae2a085baae4f0bf8f32ee2ea11af0b27260a56c324075082c98820d4e" } } ], "extra": [ 1, 134, 177, 65, 208, 136, 174, 211, 244, 227, 26, 201, 37, 127, 54, 120, 205, 193, 226, 98, 83, 44, 211, 255, 175, 232, 60, 44, 134, 170, 56, 142, 139, 2, 17, 0, 0, 0, 13, 67, 132, 109, 102, 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