Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beb8c035504c1f973e2b6c16b156e75fbd87fd802fd91466a5d590e3ea4cf874

Tx prefix hash: 37f769a4327df718e1cfe3d803b57e9d6f13a1eea4d29cdb25974215bfb9f09a
Tx public key: 0428f4b48d70dd9cebdb959c3b584233e84b746da44251cbacd3ab370fcfe512
Timestamp: 1697514317 Timestamp [UCT]: 2023-10-17 03:45:17 Age [y:d:h:m:s]: 01:095:10:20:50
Block: 871334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329417 RingCT/type: yes/0
Extra: 010428f4b48d70dd9cebdb959c3b584233e84b746da44251cbacd3ab370fcfe512021100000004faf35c9c000000000000000000

1 output(s) for total of 0.795992133000 dcy

stealth address amount amount idx
00: 1ea83e7a417a645afaa578634a2edf6458ec968b31ae807113853aa46eaa0fcb 0.795992133000 1326315 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": 871344, "vin": [ { "gen": { "height": 871334 } } ], "vout": [ { "amount": 795992133, "target": { "key": "1ea83e7a417a645afaa578634a2edf6458ec968b31ae807113853aa46eaa0fcb" } } ], "extra": [ 1, 4, 40, 244, 180, 141, 112, 221, 156, 235, 219, 149, 156, 59, 88, 66, 51, 232, 75, 116, 109, 164, 66, 81, 203, 172, 211, 171, 55, 15, 207, 229, 18, 2, 17, 0, 0, 0, 4, 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