Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bbca33076391b389bef5ce0a017fbf6063a0240a9cd34a6df798c1e1759e17d

Tx prefix hash: b0b52b6cb7d24b77d4045e0b32e497e3ad7a678c7c9f4737e397a848fb826b62
Tx public key: 98b512388c89e5e1edf0a7d9a2ee8dc7627f5dd9a2c4ad1cdbf260fa9bcb532c
Timestamp: 1708149197 Timestamp [UCT]: 2024-02-17 05:53:17 Age [y:d:h:m:s]: 01:043:16:03:17
Block: 959299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292250 RingCT/type: yes/0
Extra: 0198b512388c89e5e1edf0a7d9a2ee8dc7627f5dd9a2c4ad1cdbf260fa9bcb532c0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf554de752f7d21c73382ab5fa5a64ac0f9175d4672842d357dd352107c05be0 0.600000000000 1418834 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": 959309, "vin": [ { "gen": { "height": 959299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf554de752f7d21c73382ab5fa5a64ac0f9175d4672842d357dd352107c05be0" } } ], "extra": [ 1, 152, 181, 18, 56, 140, 137, 229, 225, 237, 240, 167, 217, 162, 238, 141, 199, 98, 127, 93, 217, 162, 196, 173, 28, 219, 242, 96, 250, 155, 203, 83, 44, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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