Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ea0dbdd1e93e496961cf8f919ed25b5850d6b8d026e8d8cbf3a0158f1ead72e

Tx prefix hash: 0545e163ec83d01010f9190230b0c5dc61dd58a3ae3dc4b449b683023922ec44
Tx public key: 8dd8b1415989b2d62c5d699fc3e586266d9232b7e5b311b1c60e90d3b16f6cc3
Timestamp: 1750609511 Timestamp [UCT]: 2025-06-22 16:25:11 Age [y:d:h:m:s]: 00:194:20:27:58
Block: 1310563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137196 RingCT/type: yes/0
Extra: 018dd8b1415989b2d62c5d699fc3e586266d9232b7e5b311b1c60e90d3b16f6cc30211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 974f96776c1a1aec034f90e37dd1df1d0ca1522536fa22f4973448783a387ec0 0.600000000000 1798184 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": 1310573, "vin": [ { "gen": { "height": 1310563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "974f96776c1a1aec034f90e37dd1df1d0ca1522536fa22f4973448783a387ec0" } } ], "extra": [ 1, 141, 216, 177, 65, 89, 137, 178, 214, 44, 93, 105, 159, 195, 229, 134, 38, 109, 146, 50, 183, 229, 179, 17, 177, 198, 14, 144, 211, 177, 111, 108, 195, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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