Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 827768c8239056be507d5d5a03cb7c8ce46dde360e3485121f3bba827939254f

Tx prefix hash: 3060805433711b16530c314b2717f311091a34417d4799fc0395aa2381b89c64
Tx public key: a6a91b145c52f2fbfa4e6887f52bc0ddbf17f3eb0fd843d8a4e718edd3388b17
Timestamp: 1703960399 Timestamp [UCT]: 2023-12-30 18:19:59 Age [y:d:h:m:s]: 01:060:23:58:37
Block: 924567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304687 RingCT/type: yes/0
Extra: 01a6a91b145c52f2fbfa4e6887f52bc0ddbf17f3eb0fd843d8a4e718edd3388b17021100000002ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e8d0ddb9ba2f928733bf7a35fa237a7909e467c0faf3d49f415e503bb575b4a 0.600000000000 1382321 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": 924577, "vin": [ { "gen": { "height": 924567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e8d0ddb9ba2f928733bf7a35fa237a7909e467c0faf3d49f415e503bb575b4a" } } ], "extra": [ 1, 166, 169, 27, 20, 92, 82, 242, 251, 250, 78, 104, 135, 245, 43, 192, 221, 191, 23, 243, 235, 15, 216, 67, 216, 164, 231, 24, 237, 211, 56, 139, 23, 2, 17, 0, 0, 0, 2, 172, 50, 141, 17, 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