Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d59d283d13f58ba072e9effe20826c541dc026356f496f8c255f6433330c927

Tx prefix hash: 3f79d5c6d8f0ee14e5674ed74394a2b2f6db34875452268e37e709f2fb5083e6
Tx public key: 554bd3b5a2a6e779929c71219bbe42fd79b20210da55cae3b329154aba6a054d
Timestamp: 1712723231 Timestamp [UCT]: 2024-04-10 04:27:11 Age [y:d:h:m:s]: 01:269:05:49:14
Block: 997211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 451199 RingCT/type: yes/0
Extra: 01554bd3b5a2a6e779929c71219bbe42fd79b20210da55cae3b329154aba6a054d021100000005e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bed4149cfce17bb3db303d23b49a276279a0b5b1a175f289fc8d9684fdb71e5 0.600000000000 1457641 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": 997221, "vin": [ { "gen": { "height": 997211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bed4149cfce17bb3db303d23b49a276279a0b5b1a175f289fc8d9684fdb71e5" } } ], "extra": [ 1, 85, 75, 211, 181, 162, 166, 231, 121, 146, 156, 113, 33, 155, 190, 66, 253, 121, 178, 2, 16, 218, 85, 202, 227, 179, 41, 21, 74, 186, 106, 5, 77, 2, 17, 0, 0, 0, 5, 224, 133, 50, 182, 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