Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 729e2cf80c52825fb27e7d7d8d2df2a4c9e8aa9898e40ee114f6ef87285079cf

Tx prefix hash: bcb5584604f12aac7fc364b54707c37fdefacdfe2479451b955474b58a688dfe
Tx public key: ad4abed2d7af103ef23b86fef4604ee7e53a0f5ce436023e2f8479acf128394c
Timestamp: 1707090161 Timestamp [UCT]: 2024-02-04 23:42:41 Age [y:d:h:m:s]: 00:345:10:43:12
Block: 950514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247301 RingCT/type: yes/0
Extra: 01ad4abed2d7af103ef23b86fef4604ee7e53a0f5ce436023e2f8479acf128394c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a4ab8e889c1fd4d401d54f339725d5bf2c0bb5a1c1aa3906006d50c90250fe8 0.600000000000 1409146 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": 950524, "vin": [ { "gen": { "height": 950514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a4ab8e889c1fd4d401d54f339725d5bf2c0bb5a1c1aa3906006d50c90250fe8" } } ], "extra": [ 1, 173, 74, 190, 210, 215, 175, 16, 62, 242, 59, 134, 254, 244, 96, 78, 231, 229, 58, 15, 92, 228, 54, 2, 62, 47, 132, 121, 172, 241, 40, 57, 76, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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