Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2af9ef4d762337e0d379822bb7a5df175744910dfb37c8447d2fef53f6ea88f1

Tx prefix hash: 25204b5583e19c891dd83a643a277b5351d228f28a34c4943b815c70836130d5
Tx public key: 0b8ef20122575d001a9881b3da8852e7c2e9c5d6a565aed84c3b15b1f47e8139
Timestamp: 1699883026 Timestamp [UCT]: 2023-11-13 13:43:46 Age [y:d:h:m:s]: 02:052:16:15:56
Block: 890779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 557501 RingCT/type: yes/0
Extra: 010b8ef20122575d001a9881b3da8852e7c2e9c5d6a565aed84c3b15b1f47e813902110000001875e3f0e9000000000000000000

1 output(s) for total of 0.686245311000 dcy

stealth address amount amount idx
00: a1e6d3c30fbd950be18ce8cfeab04efb08afd580a6e4b4ebb2cc09e46bde0baf 0.686245311000 1346810 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": 890789, "vin": [ { "gen": { "height": 890779 } } ], "vout": [ { "amount": 686245311, "target": { "key": "a1e6d3c30fbd950be18ce8cfeab04efb08afd580a6e4b4ebb2cc09e46bde0baf" } } ], "extra": [ 1, 11, 142, 242, 1, 34, 87, 93, 0, 26, 152, 129, 179, 218, 136, 82, 231, 194, 233, 197, 214, 165, 101, 174, 216, 76, 59, 21, 177, 244, 126, 129, 57, 2, 17, 0, 0, 0, 24, 117, 227, 240, 233, 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