Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4759660712a51c5960af2b40c5fe7ed6acebe30ed24e78449826866ef3e530c3

Tx prefix hash: 18d056abb69e5df4630384d7aae832ed7bdc5a0699f0f116d258efcf28e059ad
Tx public key: 24e5554787f2b7b2df1d2239d8b773c7efc8e9d1ca3e0ae35a8d15438206e576
Timestamp: 1695720999 Timestamp [UCT]: 2023-09-26 09:36:39 Age [y:d:h:m:s]: 01:154:07:42:31
Block: 856478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371324 RingCT/type: yes/0
Extra: 0124e5554787f2b7b2df1d2239d8b773c7efc8e9d1ca3e0ae35a8d15438206e57602110000000275e3f0e9000000000000000000

1 output(s) for total of 0.891523699000 dcy

stealth address amount amount idx
00: 0e73083796ec050e63a2e5aa9132bed8a7faebf4107162eb61e25c7736effd84 0.891523699000 1310554 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": 856488, "vin": [ { "gen": { "height": 856478 } } ], "vout": [ { "amount": 891523699, "target": { "key": "0e73083796ec050e63a2e5aa9132bed8a7faebf4107162eb61e25c7736effd84" } } ], "extra": [ 1, 36, 229, 85, 71, 135, 242, 183, 178, 223, 29, 34, 57, 216, 183, 115, 199, 239, 200, 233, 209, 202, 62, 10, 227, 90, 141, 21, 67, 130, 6, 229, 118, 2, 17, 0, 0, 0, 2, 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