Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f880b41f1f9bfa89c00d5a7958b6c237d5829dc36a8b18a0f52b31f2a9676574

Tx prefix hash: 0b352061f577dbb2848af6d7fce3b451035d83d930b22d77e989957650c2c8b5
Tx public key: da2fe54713bee7fe78ecffa44d4ce536ad3fd818a4527a6913f41a35a0f7183a
Timestamp: 1726760170 Timestamp [UCT]: 2024-09-19 15:36:10 Age [y:d:h:m:s]: 00:115:10:54:32
Block: 1113600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82558 RingCT/type: yes/0
Extra: 01da2fe54713bee7fe78ecffa44d4ce536ad3fd818a4527a6913f41a35a0f7183a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4f705456f3e5d480279a974c778606394c32d7189784d3e256b04c8dedc5af6 0.600000000000 1593331 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": 1113610, "vin": [ { "gen": { "height": 1113600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4f705456f3e5d480279a974c778606394c32d7189784d3e256b04c8dedc5af6" } } ], "extra": [ 1, 218, 47, 229, 71, 19, 190, 231, 254, 120, 236, 255, 164, 77, 76, 229, 54, 173, 63, 216, 24, 164, 82, 122, 105, 19, 244, 26, 53, 160, 247, 24, 58, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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