Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f1528ca2a4d3fb7f9dab3eb3359aac5ed5829ea930697901236970930b62edc

Tx prefix hash: 9c43dd6a8a9f99af3273054ca15831ce79d71df05e373293dfc69d5e25a5e705
Tx public key: 1d516e394b50f1903b6f3193fa1c08db4bac7f2dc3dd44e58661aaa101cac5d7
Timestamp: 1702096569 Timestamp [UCT]: 2023-12-09 04:36:09 Age [y:d:h:m:s]: 01:043:03:45:24
Block: 909115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292171 RingCT/type: yes/0
Extra: 011d516e394b50f1903b6f3193fa1c08db4bac7f2dc3dd44e58661aaa101cac5d7021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3f165b97daeb6eaa4288fc37c450ed39a437cbf4910f994961d7192ab1a24c5 0.600000000000 1366180 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": 909125, "vin": [ { "gen": { "height": 909115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3f165b97daeb6eaa4288fc37c450ed39a437cbf4910f994961d7192ab1a24c5" } } ], "extra": [ 1, 29, 81, 110, 57, 75, 80, 241, 144, 59, 111, 49, 147, 250, 28, 8, 219, 75, 172, 127, 45, 195, 221, 68, 229, 134, 97, 170, 161, 1, 202, 197, 215, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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