Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dca591dbf3f51cbec75d96274f142226cd9432c39418cb5d1667a2b84bab8ecb

Tx prefix hash: 3ef25cbc3fa63ec0b32706b201ffd346a9cfb066daf068633bba7c926f02b7a5
Tx public key: 81c8249cc1260c3568628c4e87f27dd7e1d73b6583d17a2004c463378f8b98e5
Timestamp: 1745409868 Timestamp [UCT]: 2025-04-23 12:04:28 Age [y:d:h:m:s]: 00:212:03:22:01
Block: 1267703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149330 RingCT/type: yes/0
Extra: 0181c8249cc1260c3568628c4e87f27dd7e1d73b6583d17a2004c463378f8b98e5021100000008dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f7b3adc49fd17fa241b5adef6d195b90f8b5fb4b60954fbb0ed259d51437ef6 0.600000000000 1754932 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": 1267713, "vin": [ { "gen": { "height": 1267703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f7b3adc49fd17fa241b5adef6d195b90f8b5fb4b60954fbb0ed259d51437ef6" } } ], "extra": [ 1, 129, 200, 36, 156, 193, 38, 12, 53, 104, 98, 140, 78, 135, 242, 125, 215, 225, 215, 59, 101, 131, 209, 122, 32, 4, 196, 99, 55, 143, 139, 152, 229, 2, 17, 0, 0, 0, 8, 219, 181, 113, 193, 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