Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75877a8e1d64ca744447eaf77e994d8227de118c2f5f3d7f7984b77f8207f58e

Tx prefix hash: 64c6f0c69eb2bd85601bb659304ad9b548dc0fa6a0c6595e12f6da869e3b0519
Tx public key: 799397744867f5800ed51d31beb5e7b2a254b3ea403c6acb06355b011c986b0b
Timestamp: 1719929513 Timestamp [UCT]: 2024-07-02 14:11:53 Age [y:d:h:m:s]: 00:350:12:11:42
Block: 1056973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250382 RingCT/type: yes/0
Extra: 01799397744867f5800ed51d31beb5e7b2a254b3ea403c6acb06355b011c986b0b0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b136136e9b1de81a6c2c513154cfe11497c0370e454b64a8f4cddec37971710 0.600000000000 1527402 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": 1056983, "vin": [ { "gen": { "height": 1056973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b136136e9b1de81a6c2c513154cfe11497c0370e454b64a8f4cddec37971710" } } ], "extra": [ 1, 121, 147, 151, 116, 72, 103, 245, 128, 14, 213, 29, 49, 190, 181, 231, 178, 162, 84, 179, 234, 64, 60, 106, 203, 6, 53, 91, 1, 28, 152, 107, 11, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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