Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 554487853f2e9cee4980b243c803b99f6a5345770ff3b9845aec4498a1fed99d

Tx prefix hash: 9cd8f06354c7f4cb1a9446c78442d38202ed2c29a4010c7accd7410a892b3a5a
Tx public key: e729893fd7bd4569e9387a644ef721a022ebb01a6df16f477d257a2a39ab0d9f
Timestamp: 1685121721 Timestamp [UCT]: 2023-05-26 17:22:01 Age [y:d:h:m:s]: 01:171:17:30:12
Block: 768650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384115 RingCT/type: yes/0
Extra: 01e729893fd7bd4569e9387a644ef721a022ebb01a6df16f477d257a2a39ab0d9f02110000000be6d27f9c000000000000000000

1 output(s) for total of 1.742383076000 dcy

stealth address amount amount idx
00: 0ccc8e11a5fa52c809c3062fd0ee1a65f0879f7d85d568619c52ac1dcfa79544 1.742383076000 1217857 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": 768660, "vin": [ { "gen": { "height": 768650 } } ], "vout": [ { "amount": 1742383076, "target": { "key": "0ccc8e11a5fa52c809c3062fd0ee1a65f0879f7d85d568619c52ac1dcfa79544" } } ], "extra": [ 1, 231, 41, 137, 63, 215, 189, 69, 105, 233, 56, 122, 100, 78, 247, 33, 160, 34, 235, 176, 26, 109, 241, 111, 71, 125, 37, 122, 42, 57, 171, 13, 159, 2, 17, 0, 0, 0, 11, 230, 210, 127, 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