Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7eccce85e5e4470c23b56d2ee13aa03244f1365063b9674e1b2d6cf37d0eb7bc

Tx prefix hash: bd1dc93d8bf13b97dc94d0d99d18efe5e4b91d1515b3c0712d051e64dd001b14
Tx public key: e4fecdb6657bc6d9f870464deaab8f7a099ed6754993dfe8f0daf2c5cbae4cc1
Timestamp: 1700991553 Timestamp [UCT]: 2023-11-26 09:39:13 Age [y:d:h:m:s]: 01:137:13:15:13
Block: 899962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359485 RingCT/type: yes/0
Extra: 01e4fecdb6657bc6d9f870464deaab8f7a099ed6754993dfe8f0daf2c5cbae4cc10211000000014b8f5122000000000000000000

1 output(s) for total of 0.639811859000 dcy

stealth address amount amount idx
00: d11d4ea65a69c73945d2c2e3e81614c53ef4ccceb65d7c0db1dd2544a9d2c526 0.639811859000 1356433 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": 899972, "vin": [ { "gen": { "height": 899962 } } ], "vout": [ { "amount": 639811859, "target": { "key": "d11d4ea65a69c73945d2c2e3e81614c53ef4ccceb65d7c0db1dd2544a9d2c526" } } ], "extra": [ 1, 228, 254, 205, 182, 101, 123, 198, 217, 248, 112, 70, 77, 234, 171, 143, 122, 9, 158, 214, 117, 73, 147, 223, 232, 240, 218, 242, 197, 203, 174, 76, 193, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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