Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea820a1748f26b10c3db39a6368f98355142abfcb6c158e06b9df924d98a2a27

Tx prefix hash: fc33019acd013461bd3e79a197839a0b856b7e3f9d03fe433363bf661f97a05e
Tx public key: 43dfb37b7f99feb13be93eb014e697c76f10251cc6d5e974c4ff2981c5e6d588
Timestamp: 1751196233 Timestamp [UCT]: 2025-06-29 11:23:53 Age [y:d:h:m:s]: 00:217:10:33:54
Block: 1315167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153449 RingCT/type: yes/0
Extra: 0143dfb37b7f99feb13be93eb014e697c76f10251cc6d5e974c4ff2981c5e6d5880211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f892a44a74c0e33e3aa8c850e0aec3de9679d1b772db84ececc97ac6c2b374d 0.600000000000 1802820 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": 1315177, "vin": [ { "gen": { "height": 1315167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f892a44a74c0e33e3aa8c850e0aec3de9679d1b772db84ececc97ac6c2b374d" } } ], "extra": [ 1, 67, 223, 179, 123, 127, 153, 254, 177, 59, 233, 62, 176, 20, 230, 151, 199, 111, 16, 37, 28, 198, 213, 233, 116, 196, 255, 41, 129, 197, 230, 213, 136, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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