Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a07d7b1ee9dd441167e7c200d220c538162cac01f438c49dd0c095fda747da1f

Tx prefix hash: 8842853245d56970abfc98d78603c99a92834316a8547fd3bfc1eb484a3b1d68
Tx public key: c583bd5c74e59543ef005bf4a6e29ad5dc0584044c4fa7c5bff3ff21d8b4ce63
Timestamp: 1716642946 Timestamp [UCT]: 2024-05-25 13:15:46 Age [y:d:h:m:s]: 00:355:22:22:02
Block: 1029735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254407 RingCT/type: yes/0
Extra: 01c583bd5c74e59543ef005bf4a6e29ad5dc0584044c4fa7c5bff3ff21d8b4ce6302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ec4ff017dfd3ce185fb6ee7caac3dd335caa9c1999dda3a4310b102e0d807e6 0.600000000000 1497908 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": 1029745, "vin": [ { "gen": { "height": 1029735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ec4ff017dfd3ce185fb6ee7caac3dd335caa9c1999dda3a4310b102e0d807e6" } } ], "extra": [ 1, 197, 131, 189, 92, 116, 229, 149, 67, 239, 0, 91, 244, 166, 226, 154, 213, 220, 5, 132, 4, 76, 79, 167, 197, 191, 243, 255, 33, 216, 180, 206, 99, 2, 17, 0, 0, 0, 5, 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