Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b16fffc01346290b196aa4b5c1d78975714a472ea854178a4a4db7b6f743146

Tx prefix hash: 1f8c49620555b0d30b7232ceed8699db86e21ae7741be9073c9c51955d1b47f0
Tx public key: 52193b08159f0a5492a12836b5e86044d0c5970d486610e47b0fa21bef7f20dd
Timestamp: 1704728649 Timestamp [UCT]: 2024-01-08 15:44:09 Age [y:d:h:m:s]: 01:101:02:19:40
Block: 930933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333375 RingCT/type: yes/0
Extra: 0152193b08159f0a5492a12836b5e86044d0c5970d486610e47b0fa21bef7f20dd02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0eeefaf2b7949fa45d81c86e9c797a58d535a0b479053d9317f7c7d1f480393 0.600000000000 1388823 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": 930943, "vin": [ { "gen": { "height": 930933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0eeefaf2b7949fa45d81c86e9c797a58d535a0b479053d9317f7c7d1f480393" } } ], "extra": [ 1, 82, 25, 59, 8, 21, 159, 10, 84, 146, 161, 40, 54, 181, 232, 96, 68, 208, 197, 151, 13, 72, 102, 16, 228, 123, 15, 162, 27, 239, 127, 32, 221, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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