Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da7ca4e16e5db644b651127583c4b02b6745b16fa35c46df74610f74d8908672

Tx prefix hash: 67ce5623763c86c22b62e77b1e5361431a98196a14a3370dc73544354c743eb4
Tx public key: 2e08586554008b1f802bb6909a982f189da81b4e0c6d5df4d71014d52032b235
Timestamp: 1682227196 Timestamp [UCT]: 2023-04-23 05:19:56 Age [y:d:h:m:s]: 02:040:15:37:24
Block: 744646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551224 RingCT/type: yes/0
Extra: 012e08586554008b1f802bb6909a982f189da81b4e0c6d5df4d71014d52032b235021100000001e7ace25d000000000000000000

1 output(s) for total of 2.092564704000 dcy

stealth address amount amount idx
00: 2c46f6e0b214d83e05a71e7a85cce6b4ba4beb8777e191333ecea432dc5cafa0 2.092564704000 1192005 of 0

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": 744656, "vin": [ { "gen": { "height": 744646 } } ], "vout": [ { "amount": 2092564704, "target": { "key": "2c46f6e0b214d83e05a71e7a85cce6b4ba4beb8777e191333ecea432dc5cafa0" } } ], "extra": [ 1, 46, 8, 88, 101, 84, 0, 139, 31, 128, 43, 182, 144, 154, 152, 47, 24, 157, 168, 27, 78, 12, 109, 93, 244, 215, 16, 20, 213, 32, 50, 178, 53, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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