Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e07449eb3118883fb345308ccd45edc1b1e3cbff6eb33160f4f6e706250fe43

Tx prefix hash: ba46414e5391f3871a0744cafe0df1c5de2e2fdf8faf17385776a69b751c85fc
Tx public key: 6de66c3f070decf2612c27d7b30e5a71cbcef64ee3736f0acd361456d34e0c0a
Timestamp: 1704829189 Timestamp [UCT]: 2024-01-09 19:39:49 Age [y:d:h:m:s]: 01:047:12:03:03
Block: 931770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295016 RingCT/type: yes/0
Extra: 016de66c3f070decf2612c27d7b30e5a71cbcef64ee3736f0acd361456d34e0c0a02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b7cb5760f399607c0f08341983555d992d40c8121d1f2907a7255a1a4db753e 0.600000000000 1389674 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": 931780, "vin": [ { "gen": { "height": 931770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b7cb5760f399607c0f08341983555d992d40c8121d1f2907a7255a1a4db753e" } } ], "extra": [ 1, 109, 230, 108, 63, 7, 13, 236, 242, 97, 44, 39, 215, 179, 14, 90, 113, 203, 206, 246, 78, 227, 115, 111, 10, 205, 54, 20, 86, 211, 78, 12, 10, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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