Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8e995d3dec5332e90d135d73905dc162cbd27efdedc8d636122a4362ddce346

Tx prefix hash: 469f0469de00a0f2d0bb9a20a7a8251aa4003ffa15821b899008b461a28b8bc7
Tx public key: b7d2c63b939128cfb9658862c11e1c527c4fbdc452ea529c75ad2c9a16a1dce0
Timestamp: 1740175666 Timestamp [UCT]: 2025-02-21 22:07:46 Age [y:d:h:m:s]: 00:229:00:36:27
Block: 1224348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161401 RingCT/type: yes/0
Extra: 01b7d2c63b939128cfb9658862c11e1c527c4fbdc452ea529c75ad2c9a16a1dce00211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f535247d1dad93c755c39f15f9aa7fc8d37bf84e4189cb5cbeaa9285b4a37037 0.600000000000 1711207 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": 1224358, "vin": [ { "gen": { "height": 1224348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f535247d1dad93c755c39f15f9aa7fc8d37bf84e4189cb5cbeaa9285b4a37037" } } ], "extra": [ 1, 183, 210, 198, 59, 147, 145, 40, 207, 185, 101, 136, 98, 193, 30, 28, 82, 124, 79, 189, 196, 82, 234, 82, 156, 117, 173, 44, 154, 22, 161, 220, 224, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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